default get_change_comments to unresolved threads - #81
Merged
Conversation
BREAKING: a bare get_change_comments call now returns unresolved threads only; pass status=all for the previous behavior. The full comment history of a long review can dwarf the context it lands in -- a change with a hundred-plus comments overflows the client's tool-result budget and forces a re-read. The actionable subset is the unresolved discussion, so that is what a bare call returns; status=all and status=resolved stay available unchanged, and the tool description steers the model to reach for the history only when the settled context matters. Notification payloads are unaffected: their thread selection is by new comment, not by resolution state.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking (agent-facing): a bare
get_change_commentscall now returns unresolved threads only — the actionable subset.status=allrestores the previous behavior;status=resolvedunchanged.Motivation: on long reviews (100+ comments) the full history overflows the client's tool-result budget and forces a re-read; the settled threads are the bulk and rarely what the agent needs.
status=allflagged as potentially very large.status=allexplicitly.Test_DeltaRenderer_ThreadParitystill green.